Hunt groups let you dial a pilot number and have the call completed to the first idle station (including voice mail, auto attendant, RAD, and IVR ports) in a group of stations. Any station within a Hunt Group may be accessed directly by dialing the station number.
There are several types of hunt groups (for example, Voice, RAD, Voicemail, etc.) and two types of hunting: circular and terminal. In circular hunting, the search for an idle station begins at the station after the last one to receive a call. In terminal hunting, the search for an idle station begins at the first station programmed in the Hunt Group. In both cases, the search progresses through all stations in the Hunt Group in a programmed sequence.
If there is a free member in the hunt group, that station is rung by a caller who accesses the group. If the hunt group is busy, one of the following operations take place:
An internal caller receives busy tone and has the option of going on-hook, setting a callback, or camping on.
A DIL caller receives ringback tone (from the CO or the distant system) and is placed in a first-in, first-out call queue within the system.
A DID trunk caller receives busy tone.
A transferred trunk call receives music or silence.
The first member of the hunt group to become free is connected to the next waiting caller.
You must program the leading digits
of the hunt group pilot number to be greater than its RAD group numbers.
When the system backs up or restores Hunt Groups, it does so in the
order of the leading digits of the hunt group pilot number. If the
leading digit of the hunt group number is lower than its RAD group
number, the system will be unable to back up or restore the RAD group
data and the system will display an error message (for example: "RAD
group must be a number that will be DATA RESTORED before the pilot
number").
The following table provides some examples to illustrate this requirement:
Hunt Group Number |
RAD Group Number |
Backup/Restore Successful |
2 |
1 |
Yes |
9 |
7 |
Yes |
1 |
2 |
No |
13 |
7 |
No (leading digit 1 is not greater than RAD group number 7) |
Override cannot be performed on a Hunt Group. If you attempt to Override, you will hear reorder tone.
Personal ring group and Multi-device user group DNs can be included in Emergency Hunt Groups.
A Hot Desk user cannot be a member of an Emergency Hunt Group or a Recorder Hunt Group.
A Hot Desk user cannot log into a Registration DN that is a member of an Emergency Hunt Group or a Recorder Hunt Group.
Sets with Line Interface Modules configured should NOT be configured as members of Emergency Hunt Groups.
69xx devices configured with Mobile Line keys CANNOT be members of an Emergency Hunt Group.
The following phones can be members of an Emergency Hunt Group: 5140, 5220/5220 Dual Mode, 5224/5224 Dual Mode, 5240, 5320/5320e, 5324, 5330/5330e, 5340/5340e, 5360, 5560 IP Turret, 69xx IP Phones, CitelLink Type2, DeTeWe Link Type 1, Navigator, PKM96, Spectralink Type 1.
To ensure the consistent application of COS across all members of a hunt group, ensure that you program the hunt group and hunt group members with the same COS.
The Hunt Group COS (or, if no Hunt Group COS is programmed, the COS of the first member of the Hunt Group) is used for the following COS options:
Call Reroute after CFFM to busy destination
COV/ONS/E&M Voice Mail Port
ONS/ OPS Internal Ring Cadence for External Callers (only if the first member is ONS/OPS)
Answer Plus Delay To Message Timer
Answer Plus System Reroute Timer
Call Forward - No Answer Timer
If members of a hunt group share a Key System line and the hunt group also includes ACD sets, ensure that a non-ACD set has the lowest directory number. After a database restore, phones get restored in numerical order. If the first phone in the Multiline Appearance Groups form is an ACD set, you cannot call the hunt group until that agent logs in.
When a call comes to a hunt group that supports the use of multi-colored LED functionality (to indicate the activity status of calls), the line key LED indicator will either flash or should the call go unanswered, the LEDs will turn off.
If an external call is made to a VoiceMail hunt group with no available members and the COS option Auto Campon Timer is blank, the caller listens to a ringback tone until a port becomes available.
The following table shows the maximum number of supported hunt groups and hunt group members, based on the MiVoice Business platform type and whether the Extended Hunt Group option in the License and Option Selection form is enabled or disabled.
Platform |
Extended Hunt Group |
Groups |
Members per Group |
Total Members |
Server-based MiVoice Business controllers |
Enabled |
64 |
1000 | 64000 |
|
Disabled |
2000 |
64 |
128000 |
All other controllers |
Enabled |
16 |
50 |
4000 |
Disabled |
176 |
64 |
11264 |
Hunt
Groups form
Enter the Pilot Number, Hunt Group Mode, Hunt Group Type and other required parameters.
Enter the Directory Number of each hunt group member.
NOTE: The order in which the numbers are entered affects the order in which the hunt is conducted.
IMPORTANT
The method of searching hunt groups can have a significant effect on the overall performance of a system. Terminal hunt groups are good for a small number of ports (e.g. RADs) but can be extremely slow and CPU intensive with a large number of members. Large hunt groups should be configured for circular hunting for optimum performance.
Auto attendant ports or IVR ports should be configured as "VoiceMail" type hunt groups which provides auto camp-on capability. Other hunt group types do NOT provide auto camp-on. Without it, high traffic sites may experience system slowdowns if calls are rejected by call control due to excessive processing.
Not applicable
None